-
Notifications
You must be signed in to change notification settings - Fork 64
Create GitHub action to automate mcad release #427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create GitHub action to automate mcad release #427
Conversation
b51a06f
to
6f4fade
Compare
Changes look ok to me, though I am not so familiar with MCAD Makefile implementation to review Makefile changes. |
Sure.. Seems i missed to update CONTROLLER_VERSION file deletion changes to incorporate in Dockerfile and deployment/Makefile.. I will update it |
6f4fade
to
1d7cbee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation updates, indentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, It would be great if we can create branches per release. creating an automated branch could be a follow-up PR but this is needed for sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Workflow doesn't work properly based on experiments with my fork.
I have yet to test this workflow, will update PR with new changes as per review comments and will test it |
09bdaca
to
6fd9de2
Compare
6fd9de2
to
059b5c3
Compare
I tested this workflow on https://github.com/Srihari1192/multi-cluster-app-dispatcher/actions/workflows/mcad-release.yml looks good |
Fixes #408